Setting advanced connection properties

In the Advanced tab, you can set the following properties:

• Maximum Buffer Size for Read (KB): Specify the maximum number of bytes to read each time the log is accessed during Change Processing. If you encounter performance issues, adjusting this number may help.

• Change Data Capture: To enable data capture from IBM DB2 for LUW, the source tables need to be created as follows:

  CREATE / ALTER TABLE table-name …. DATA CAPTURE CHANGES [INCLUDE LONGVAR COLUMNS];

  You can either configure Replicate to perform this operation by selecting Automatically enable DATA CAPTURE CHANGES (requires admin privilege) in the endpoint settings or you can do this manually by selecting Let DBA set up data capture.

• Check for changes every (sec): How often to check the source database for changes.

Internal parameters

Internal parameters are parameters that are not exposed in the UI. You should only use them if instructed by Qlik Support.

To add internal Qlik Replicate parameters:

1. Click the Internal Parameters link.

   The Internal Parameters dialog box opens.

2. In the edit box, type the name of the parameter you need to add and then click it.
3. The parameter is added to the table below the search box with its default value.
4. Change the default value as required.
5. To reset the parameter value to its default, click the "Restore default value" icon at the end of the row.

More options

These options are not exposed in the UI as they are only relevant to specific versions or environments. Consequently, do not set these options unless explicitly instructed to do so by Qlik Support or product documentation.

To set an option, simply copy the option into the Add feature name field and click Add. Then set the value or enable the option according to the instructions you received.

Settings summary

You can view a summary of your settings by clicking the Setting Summary link. This is useful if you need to send a summary of your settings to Qlik Support.

Resuming or starting a task from LRI in a pureScale environment

To resume or start a task from LRI in a pureScale environment:

1. Run the db2pd DB2 command line to determine the Current Log Number:

   $ db2pd -log -db database_name

   where database_name is the name of your database.

   The output will be similar to the following:

   Database Member 0 -- Database SAMPLE -- Active -- Up 0 days 00:27:02 -- Date 2018-05-23-14.49.45.515600
   Logs:
   Current Log Number            2
   Pages Written                 19
   Cur Commit Disk Log Reads     0
   Cur Commit Total Log Reads    0
   Method 1 Archive Status       n/a
   Method 1 Next Log to Archive  n/a
   Method 1 First Failure        n/a
   Method 2 Archive Status       n/a
   Method 2 Next Log to Archive  n/a
   Method 2 First Failure        n/a
   Log Chain ID                  0
   Current LSO                   57142478
   Current LSN                   0x000000000004FB14
    
   Address            StartLSN         StartLSO    State Size       	Pages      Filename
   0x00007F164E99F090 00000000000429EC 48912001    0x00000000 1000       1000       S0000000.LOG
   0x00007F16511319F0 000000000004901E 52988001    0x00000000 1000       1000       S0000001.LOG
   0x00007F1651132350 000000000004F9A6 57064001    0x00000000 1000       1000       S0000002.LOG
   

   The most recent (current) log is number 2.

2. Run the db2flsn command to determine the LRI/ LSN range of that log file:

   $ db2flsn -db SAMPLE -lrirange 2

   The output will be similar to the following:

   S0000002.LOG: has LRI range
   00000000000000010000000000002254000000000004F9A6 to
   000000000000000100000000000022CC000000000004FB13

   In the above output, the task "Start From" LRI value would be:

   0100000000000022CC000000000004FB13 (i.e. the 34 bytes at the end of the range).

Unable to retrieve the current LSN?

If you are unable to retrieve the current LSN, you can instruct Replicate to scan the log by specifying CurrentLSN=scan (as described in Internal parameters) instead of the current LSN.